Enforcing parameters for quality of data link service at a future time

ABSTRACT

A method is provided for enforcing quality of service parameters. A gateway receives a request for data usage from a mobile device. The gateway sends, to a controller, inquiry for allowed bit rate. Upon receiving a first bit rate value, the gateway sends, to a charging system, request for quota. In response to receiving the quota, the gateway provides data to the mobile device based on the first bit rate value. The gateway provides data to the mobile device until the quota is exhausted. Once a data usage threshold is reached, the gateway receives, from the controller, a second bit rate value. In response to receiving the second bit rate value, the gateway provides data to the mobile device based on the second bit rate value, until an activation-time is reached. When the activation-time is reached, the gateway resets the allowed bit rate to the first bit rate value.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/002,291, entitled “Enforcing Parameters for Quality of Data LinkService at a Future Time”, filed on Jan. 20, 2016, the entirety of whichis incorporated by reference herein.

BACKGROUND

Long Term Evolution (LTE) standard, also referred to as 4G LTE, providesregulations for wireless communication of high-speed data for mobilephones and data terminals. The network technologies providing thewireless communication can increase the capacity and speed using adifferent radio interface together with core network improvements. Awireless network provider typically registers a customer with a specificdata plan determining the data usage limit for the customer andcustomers can sign up for data plans based on their need for data andfor the access speed. For example, a customer with extreme data needsmay sign up for an unlimited data plan, which allows the customer to useas much data as desired during a billing cycle. However, such customerswith unlimited data access behavior may impact the user experience ofother customers within the same Radio Access Network (RAN) section.Wireless network providers can use mechanisms such as, for example,bandwidth throttling to effectively manage the network resources andensure network reliability by preventing the heaviest usage customersfrom causing congestion to other customers. For example, for customerswith unlimited data plan, when data usage within a billing cycle exceedsa certain threshold, (e.g. 5 Gigabytes), the network can put thecustomers on a lower speed for the rest of the billing cycle. In thiscase, at the start of a new billing cycle, the restriction can beremoved and the customers can resume high data speed.

However, at the billing cycle reset time, potentially high volume ofmessages need to be exchanged within the network for removing the speedrestriction on the customers with applied restriction. This is becausethe current network standards do not provide a mechanism to set commandlevel parameters to take effect in a future time.

Therefore, a need exists for a mechanism to throttle customer bandwidthonce data usage threshold by that customer is reached, and enforceresumption of high speed data access at a future time such as the starttime of a new billing cycle.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord withthe present teachings, by way of example only, not by way of limitation.In the figures, like reference numerals refer to the same or similarelements.

FIG. 1 illustrates a high-level functional block diagram of a dataservice provider providing data services to customers, where bandwidththrottling is applied.

FIG. 2 illustrates an exemplary process of bandwidth throttling by adata service provider, based on a usage threshold.

FIG. 3 illustrates an exemplary process of resuming high speed dataservice at start of a new billing cycle, according to oneimplementation.

FIG. 4 illustrates an exemplary process of resuming high speed dataservice at start of a new billing cycle, according to anotherimplementation.

FIG. 5 is a high-level functional block diagram of an exemplarynon-touch type mobile device that may utilize the enforced quality ofservice parameters through a network/system like that shown in FIG. 1.

FIG. 6 is a high-level functional block diagram of an exemplary touchscreen type mobile device that may utilize the enforced quality ofservice parameters through a network/system like that shown in FIG. 1.

FIG. 7 is a simplified functional block diagram of an exemplary computerthat may be configured as a host or server.

FIG. 8 is a simplified functional block diagram of an exemplary personalcomputer or customer device.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth by way of examples in order to provide a thorough understanding ofthe relevant teachings. However, the present teachings may be practicedwithout such details. In other instances, well known methods,procedures, components, and/or circuitry have been described at arelatively high-level, without detail, in order to avoid unnecessarilyobscuring aspects of the present teachings.

As wireless communication of high-speed data for mobile phones and othercomputing devices becomes more popular and the number of wireless datausers increase, there has to be some way to control the bandwidthallowed to individual users. Long Term Evolution (LTE) standards, whichprovide regulations for wireless communication of high-speed data,include parameters for controlling the bandwidth allowed for a user. Abandwidth control parameter is referred to as Aggregate Maximum Bit Rate(AMBR). AMBR defines the maximum possible bit rate allowed for aparticular LTE user for all of their “best effort” or non-guaranteed bitrate data services so that the user cannot hog the available bandwidthfrom the other LTE users. Different AMBR values can be used by the LTEsuch as, for example, UE-AMBR, the maximum possible bit rate configuredby the LTE operator for a particular LTE user equipment (UE) or customerdevice, for their best effort services; and APN-AMBR, the maximumpossible bit rate configured by the LTE operator for a particular LTEuser for their best effort services on one particular packet datanetwork as defined by an access point name (APN).

However, even with assigned bandwidths, a customer with unlimitedallowed data may need to be allowed a limited bandwidth after a certaindata usage threshold is reached. For example, when a customer withunlimited data plan exceeds 5 Gigabytes of data usage during a billingcycle (e.g., a month) the network provider may introduce setting tolimit data usage for that customer for the remainder of the billingcycle and resume providing the full bandwidth to the user when thebilling cycle is reset and a new billing cycle is started (e.g., end ofthe month). The intentional slowing of data service (e.g., via theInternet) is referred to as bandwidth throttling. Bandwidth throttlingis a reactive measure employed in communication networks to regulatenetwork traffic and minimize bandwidth congestion. Bandwidth throttlingcan occur at different locations on the network. For example, on a localarea network (LAN), a system admin may employ bandwidth throttling tohelp limit network congestion and server crashes. On a broader level,the Internet service provider may use bandwidth throttling to helpreduce a user's usage of bandwidth that is supplied to the localnetwork.

Bandwidth throttling can be used to actively limit a user's upload anddownload rates on programs such as video streaming, and file sharingapplications, as well as even out the usage of the total bandwidthsupplied across all users on the network. Bandwidth throttling is alsooften used in Internet applications, in order to spread a load over awider network to reduce local network congestion, or over a number ofservers to avoid overloading individual servers, and so reduce theirrisk of crashing, and gain additional revenue by compelling users to usemore expensive pricing schemes where bandwidth is not throttled.

Reference now is made in detail to the examples illustrated in theaccompanying drawings and discussed below. FIG. 1 illustrates ahigh-level functional block diagram of a data service provider 100providing data services to customers, where bandwidth throttling isapplied. The network 100 illustrated in FIG. 1 includes an OnlineCharging System (OCS) 101, a Policy and Charging Rules Function (PCRF)103, and a Policy and Charging Enforcement Function (PCEF) 105. The PCEF105 is included in a Gateway (PGW 107).

The PCRF 103 is a dedicated policy functional entity that providesnecessary policy functions for bandwidth and charging of customers onmultimedia networks. The PCEF 105 is the functional entity whichincludes policy enforcement along with data flow based chargingfunctionalities. This functional element is located at the Gateway 107and is responsible of providing controller functions in traffic handlingand Quality of Service (QoS) at PGW 107 over the user plane traffic, andproviding service data flow detection, including online and offlinedifferent charging interactions. QoS refers to certain characteristicsof a data link connection as observed between the connection endpoints.QoS describes the specific aspects of a data link connection that areattributable to the data service provider. The PCRF 103 is designed toprovide network control relating to the service data flow detection,QoS, and flow based charging controlling to the PCEF 105, whereas PCEF105 basically provides user traffic handling and QoS at PGW 107.

The service provider 100 can throttle customer data for a customerdevice 111 a-111 n when a data usage threshold by a customer device 111a-111 n is reached. For example, the OCS 101 can notify PCRF 103 via Syinterface 113 that data usage threshold by a device 111 a-111 n isreached. Upon receiving the notification from OCS 101, the PCRF 103 cannotify PCEF 105 within the PGW 107, via Gx interface 115, to enforce alower APN-AMPR for device 111 a-111 n.

However, at the end of a billing cycle, the initial APN-AMBR associatedwith the service defined for device 111 a-111 n should be resumed. Whenthe end of a billing cycle is approaching, the OCS 101 can notify thePCRF 103 via Sy interface 113 that end of the billing cycle isapproaching. Upon receiving the notification, the PCRF 103 can send a Gxmessage via Gx interface 115 to the PCEF 105 at the billing cycle resettime to change the APN-AMBR to the initial bit rate and resume theservice with the speed assigned to device 111 a-111 n.

At the billing cycle reset time (when a validity time expires),potentially high volume of Gx messages may be exchanged between the PCRF103 and PGW 107. The reason is that the existing Gx standards do notprovide a mechanism to set command level QoS parameters to take effectat a future time (e.g., at the start of a new billing cycle).

In one implementation of the disclosure, a mechanism for pre-setting thecommand level QoS parameters is provided, such that the pre-setparameters can be activated at a future time when predefined conditionsare met, for example, at the start of a new billing cycle. As a result,traffic due to excessive exchange of Gx messages between the PCRF 103and the PGW 107 can be avoided. The disclosed mechanism can notify thePGW 107 ahead of time to avoid potential message storm.

Although the communication network is described to be an LTE network inthe present application, it may be applicable to other types ofnetworks. The customer devices 111 a-111 n may be capable of voicetelephone communications through the network 109, and for accessingapplications and services provided by various application servers (notshown). The exemplary devices 111 a-111 n are capable of datacommunications through the particular type of network 109 (and the usersthereof typically will have subscribed to data service through thenetwork). The customer devices 111 a-111 n are also capable ofestablishing radio communications such as Near Field Communication (NFC)with each other and with other devices.

Customer devices 111 a-111 n can take the form of portable handsets,smartphones or personal digital assistants, although they may beimplemented in other form factors. Program applications, provided by theservice provider 100 to the customer devices 111 a-111 n can beconfigured to execute on many different types of customer devices 111a-111 n. For example, a mobile device application can be written toexecute on a binary runtime environment for (BREW-based) mobile device,a Windows Mobile based mobile device, Android, I-Phone, Java Mobile, orRIM based mobile device such as a BlackBerry or the like. Some of thesetypes of devices can employ a multi-tasking operating system.

The communication network 109 can be implemented by a number ofinterconnected networks. Hence, the overall network illustrated in FIG.1 may include a number of radio access networks (RANs), as well asregional ground networks interconnecting a number of RANs and a widearea network (WAN) interconnecting the regional ground networks to corenetwork elements. A regional portion of the network 10, such as thatserving customer devices 111 a-111 n, can include one or more RANs and aregional circuit and/or packet switched network and associated signalingnetwork facilities.

Physical elements of a RAN operated by one of the mobile serviceproviders or carriers include a number of base stations (not shown). Abase station can include a base transceiver system (BTS), which cancommunicate via an antennae system at the site of base station and overthe airlink with one or more of the customer devices 111 a-111 n, whenthe customer devices are within range. Each base station can include aBTS coupled to several antennae mounted on a radio tower within acoverage area often referred to as a “cell.” The BTS is the part of theradio network that sends and receives Radio Frequency (RF) signalsto/from the customer devices 111 a-111 n that are served by the basestation.

A customer device 111 a-111 n communicates over the air with a basestation and through the communication network 109 for various voice anddata communications, e.g. through the Internet (not shown with a serviceprovider 100). To insure that the data services offered by the serviceprovider 100, are available to only authorized devices/users, theproviders of the services may also deploy an authentication service. Forexample, the service provider 100 may request from the user to enter apassword, a biometric input such as a fingerprint, etc. and compare theentry with a password or biometric input on file in a memory location ofthe service provider 100, prior to allowing the user of the customerdevice 111 a-111 n to proceed with receiving a service.

FIG. 2 illustrates an exemplary process of bandwidth throttling by adata service provider, based on a data usage threshold. The process ofFIG. 2 is explained herein using the example scenario as discussed withregards to FIG. 1. In this example, it is assumed that a user of acustomer device 111 a-111 n is subscribed to a data service provided bythe service provider 100 of FIG. 1. The customer device 111 a-111 n maybe subscribed for an unlimited data service. The service provider 100may provide data to customer devices 111 a-111 n with an APN-AMBR valueof, for example, 150 Megabytes per second.

However, the service provider 100 may apply bandwidth throttling suchthat when the customer device 111 a-111 n reaches a 5 Gigabytes datausage threshold, a reduced APN-AMBR of, for example, 200 Kilobytes persecond is enforced until the end of the current billing cycle. Uponstarting a new billing cycle, the APN-AMBR is reset to the initial 150Megabytes per second. As illustrated in FIG. 2, at step 201, the PGW 107sends an inquiry for the allowed bit rate associated with the customerdevice 111 a-111 n to the PCRF 103 and at step 203 the PGW 107 receivesthe APN-AMBR value 150 Megabytes per second from the PCRF 103.

Upon receiving the APN-AMBR, at step 205, the PGW 107 sends a requestfor a quota for the customer device 111 a-111 n to the OCS 101. Thequota may include all of the remaining data assigned to the customerdevice 111 a-111 n or may include slice of the remaining data assignedto the customer device 111 a-111 n until the data usage threshold forthe customer device 111 a-111 n is reached. For example, if the datausage threshold is 5 Gigabytes and the customer device 111 a-111 n hasalready used 4.5 Gigabytes of data during the current billing cycle, thequota for the customer device 111 a-111 n may be 0.5 Gigabytes.Alternatively, the quota may be a slice of 0.5 Gigabytes (e.g., 0.3Gigabytes). At step 207, the PGW 107 receives the quota and a validitytime (VT) from the OCS 101 (e.g., 0.5 Gigabytes). In response toreceiving the quota form the OCS 101, the PGW 107 can provide data tothe customer device 111 a-111 n based on the APN-AMBR (e.g., 150Megabytes per second) via the communication network 109

Once either the quota is exhausted or the validity time has expired, thePGW 107 may send another request for quota to the OCS 101 as illustratedin Step 209. In response, the PGW 107 may receive an updated quotaand/or an updated validation time. The PGW 107 may repeatedly send theremaining quota request to OCS 101 and receive the updated quota, untilthe data usage threshold of 5 Gigabytes is reached (shown as 221).

The PGW 107 may monitor data usage by the customer device 111 a-111 nand determine the used quota based on the monitoring. Alternatively, thePCRF 103 may receive a notification from the OCS 101 indicating that thedata usage threshold is reached. Subsequently, the PCRF 103 can send anotification of the data usage threshold reaching to the PGW 107. Whenthe data usage threshold is reached, at point 221, additional quota maybe granted to the customer device 111 a-111 n via the OCS 101 at step211. At point 221, the OCS 101 may set a parameter indicating that thedata usage threshold for customer device 111 a-111 n is reached.

Upon reaching the data usage threshold, at step 213, the OCS 101 sends aspending status notification request (SNR) for the customer device 111a-111 n to PCRF 103. The SNR may include policy counter status (e.g.,spending status) for the customer device 111 a-111 n. Upon receiving thenotification from OCS 101, the PCRF 103 may reduce the APN-AMBR for thecustomer device 111 a-111 n, and at step 215 the PCRF 103 provides ananswer to the SNR (SNA) to the OCS 101 indicating receipt of the SNR.

At step 217, the PGW 107 receives a reduced APN-AMBR (e.g., 200Kilobytes per second) from the PCRF 103 for the customer device 111a-111 n. In response to receiving the reduced APN-AMBR, the PGW 107 maysend an answer to PCRF 103, per step 219, indicating receipt of thereduced APN-AMBR. The PGW 107 may continue providing data to thecustomer device 111 a-111 n based on the reduced APN-AMBR of 200Kilobytes per second until the end of the current billing cycle.However, according to the known standards of the Gx interface 115, atthe end of the billing cycle, the PCRF 103 has to send a notificationmessages to the PGW 107 via the Gx interface 115 to notify the PGW 107to reset the APN-AMBR to the initial value of 150 Megabytes per second.Since the PCRF 103 has to send the end of billing cycle notificationsfor multiple customer devices 111 a-111 n, excessive number ofnotifications may cause excessive traffic on the Gx interface 115.

In one implementation of the disclosure, the PGW 107 uses a predefinedactivation time to provide data to the customer device 111 a-111 n basedon the reduced APN-AMBR. When the predefined activation time is reached,the PGW 107 may reset the APN-AMBR for the customer device 111 a-111 nto the initial value of 150 Megabytes per second or to a new APN-AMBRprovided by the PCRF 103. The PGW 107 may receive a new APN-AMBR fromthe PCRF 103 at the start of a new billing cycle to resume providingdata to the customer device 111 a-111 n based on the new APN-AMBR. Atypical process for the high speed data service resumption is furtherdiscussed with regards to FIG. 3.

FIG. 3 illustrates an exemplary process of resuming high speed dataservice at start of a new billing cycle, according to oneimplementation. It is assumed that the process of FIG. 3 follows theprocess of FIG. 2. For example, step 301 may be the next step followingthe step 219 of FIG. 2. At steps 301 and 303, the PGW 107 may repeatedlysend requests for remaining quota for the customer device 111 a-111 n tothe OCS 101 and receive updated quota from OCS 101, until the OCS 101 atpoint 321 determines that a billing cycle reset is approaching. Upon thedetermination of the billing cycle reset time, at step 305 the OCS 101sends a spending notification request for the customer device 111 a-111n to the PCRF 103. The spending notification request may include policycounter status for the customer device 111 a-111 n. At step 307, thePCRF 103 sends an answer to the request to OCS 101. The policy counterstatus may indicate that the APN-AMBR associated with the customerdevice 111 a-111 n is at the start of the new billing cycle.

At step 309, prior to the start of a new billing cycle (shown as 323)the PGW 107 receives a revalidation notification from the PCRF 103 forthe customer device 111 a-111 n. The revalidation notification includesa request for the PGW 107 to revalidate the APN-AMBR for the customerdevice 111 a-111 n at a time indicated in the notification. In responseto receiving the revalidated APN-AMBR, the PGW 107 may send an answer toPCRF 103, per step 311, indicating receipt of the revalidatingnotification. In this example, at point 323 when a new billing cyclestarts (e.g. at the midnight of the last day of a current billing cycle)the PGW 107 can start providing data to the customer device 111 a-111 nbased on the revalidated APN-AMBR.

Upon start of the new billing cycle, at step 313 the PGW 107 can send arequest for the new APN-AMBR to the PCRF 103 and at step 315 the PGW 107receives the new value (e.g., 150 Megabytes per second) for the APN-AMBRfrom the PCRF 103. The APN-AMBR may remain the same as the previousbilling cycle (e.g., 150 Megabytes per second). Alternatively, a newAPN-AMBR may be introduced for the new billing cycle. For example, adata plan for the customer device 111 a-111 n may have been updatedduring the previous billing cycle and the updates may be effective atthe start of the new billing cycle. In such cases, the PCRF 103 mayprovide, at step 315, an updated APN-AMBR for the new data plan for thecustomer device 111 a-111 n to the PGW 107.

At steps 317 the PGW 107 sends a request for remaining quota for thecustomer device 111 a-111 n to the OCS 101. Upon receiving the firstrequest 317 in the new billing cycle, the OCS 101 can reset theparameter that was set at point 221 of FIG. 1 indicating that the datausage threshold is reached to indicate that the data usage threshold isnot reached (shown as point 325).

The PGW 107 may repeatedly send requests for remaining quota for thecustomer device 111 a-111 n to the OCS 101 (317) and receive updatedquota from OCS 101 (319). For example, the PGW 107 can repeatedly sendcredit control requests (CCRs) to OCS requesting additional quota. Aspreviously discusses, OCS can send additional quota and VT (validitytime) in a credit control answer (CCA) to the PGW 107. Once theadditional quota is exhausted or VT expires, PGW 107 sends another CCR-Uto OCS. PGW 107 can determine whether the quota granted in CCA is usedby the customer device 111 a-111 n or the VT is expired. The VT mayindicate a time interval, upon expiration of which the PGW 107 shouldrequest a status update of data usage by the customer device 111 a-111 nfrom the OCS 101.

FIG. 4 illustrates an exemplary process of resuming high speed dataservice at start of a new billing cycle, according to anotherimplementation. It is assumed that the process of FIG. 4 follows theprocess of FIG. 2. For example, step 401 may be the next step followingthe step 219 of FIG. 2. At steps 401 and 403, the PGW 107 may send arequest for remaining quota for the customer device 111 a-111 n to theOCS 101 and receive updated quota from OCS 101. The OCS 101 maydetermine, at point 417, that a billing cycle reset is approaching. Uponthe determination of the billing cycle reset time, at step 405, the OCS101 sends a spending notification request for the customer device 111a-111 n to the PCRF 103. The spending notification request may includepolicy counter status for the customer device 111 a-111 n. At step 407,the PCRF 103 sends an answer to the request to OCS 101. The policycounter status may indicate the APN-AMBR associated with the customerdevice 111 a-111 n at the start of the new billing cycle.

At step 409, prior to the start of a new billing cycle (shown as 419)the PGW 107 receives QoS information for the customer device 111 a-111 nfrom PCRF 103. The start of billing cycle 419 may be different fordifferent customer devices 111 a-111 n. For example, for one customerdevice 111 a-111 n the billing cycle may start on the first day of eachmonth while for another customer device 111 a-111 n the billing cyclemay start on the 10^(th) day of the month. The QoS information mayinclude a priority parameter for the customer device 111 a-111 n toprioritize the customer device 111 a-111 n over other customer devices111 a-111 n during the time of high congestion in the network. The QoSinformation may also include a condition which when satisfied may givethe customer device 111 a-111 n a higher priority over other customerdevices 111 a-111 n. For example, the condition may include a date, atime, a time/date duration, etc. In one implementation, the QoSinformation may include an activation-time, such that the PGW 107 canenforce the APN-AMBR for the customer device 111 a-111 n at theactivation time.

The step 409 at which the PCRF 103 sends the QoS information to PGW 107can be pre-scheduled for each customer device 111 a-111 n based on thestart of the billing cycle for that customer device. For example thestep 409 may be performed one hour, two hours, 24 hours, etc. prior tostart of the new billing cycle. The PCRF 103 may set the activation-timeto the billing cycle reset time, include a new QoS parameters in thereauthorization request (RAR) and send it to PGW 107. The PGW 107 canstore the activation-time in a local memory and when activation-timerexpires, the PGW 107 can enforce the new QoS parameters.

In response to receiving the QoS information including, for example, theactivation time, the PGW 107 may send an answer to PCRF 103, per step411, indicating receipt of the QoS information. In this example, atpoint 419 when a new billing cycle starts (e.g. at the midnight of thelast day of a current billing cycle), the PGW 107 can start providingdata to the customer device 111 a-111 n based on the QoS informationreceived from the PCRF 103.

However, since the PGW 107 has received the activation time from PCRF103 at step 409, sending a request for the new APN-AMBR to the PCRF 103(shown in step 313 of FIG. 3) and receiving the new value for theAPN-AMBR from the PCRF 103 (shown at step 315 of FIG. 3) can be omitted.Since a large number of customer devices 111 a-111 n may use the dataservices provided by the service provider 100, omitting messages ofsteps 313 and 315 for each customer device 111 a-111 n can noticeablyreduce the network traffic.

The activation time can be set by the PCRF 103 using a new optionalfunction such as, for example an Attribute-Value Pair (AVP) added intothe Gx interface 115 standard. The new function can provide a flexibleway for the PCRF 103 to set the activation time for the QoS parameters.Similarly, a deactivation-time can be also determined using another newoptional function such as, for example, AVP added into the Gx interface115 standard. Although not shown in FIG. 4, the PCRF 103 can send thedeactivation-time to the PGW 107 at any occasion when a change in theAPN-AMBR for the customer device 111 a-111 n is needed. For example, ata congested time of the network, a policy in the PCRF 103 may requirethat the APN-AMBR for a customer device 111 a-111 n be reduced from adefault 150 Megabytes per second to a reduced 100 Megabytes per secondfor a period of time (an hour, a day, etc.). In this case, the PCRF 103can send a deactivation time to PGW 107 indicating the start time forthe reduced APN-AMBR and a deactivation-time indicating the end of thereduced APN-AMBR and start of the default APN-AMBR.

At steps 413 the PGW 107 sends a request for remaining quota for thecustomer device 111 a-111 n to the OCS 101. Upon receiving the firstrequest 413 in the new billing cycle, the OCS 101 can reset theparameter that was set at point 221 of FIG. 1 indicating that the datausage threshold is reached to indicate that the data usage threshold isnot reached (shown as point 421).

The PGW 107 may send requests for remaining quota for the customerdevice 111 a-111 n to the OCS 101 (413) and receive updated quota andvalidity time from OCS 101 (415). The PGW 107 can provide data access tothe customer device 111 a-111 n until the updated quota is exhausted orthe validity time has expired. In response, the PGW 107 may send arequest for remaining quota to OCS 101 and receive another updated quotaand validity time. This process may continue until the data usagethreshold (e.g., 5 Gigabytes) is reached. The PGW 107 may receive anotification from OCS 101 indicating that the data usage threshold isreached. In some cases, the PCRF 103 may also receive a notificationfrom the OCS 101 indicating that the data usage threshold is reached.Subsequently, the PCRF 103 can send a notification of the data usagethreshold reaching to the PGW 107. Additionally or alternatively, thePGW 107 may itself monitor data usage by the customer device 111 a-111 nand determine the remaining quota based on the monitoring.

As previously discussed, in one implementation, the PCRF 103 candetermine an activation-time and a deactivation-time for the APN-AMBR ofa customer device 111 a-111 n based on the QoS information and datausage limit of the customer device. Example (1) illustrates a sample ofnew optional functions added into the Gx interface 115 standard fordetermining the activation-time and the deactivation-time by the PCRF103. These example AVPs provide information on when the QoS parameterswould be activated or deactivated.

-   -   [V] [M] QoS-Information:    -   [V] APN-Aggregate-Max-Bit rate-DL: 75000000    -   [V] APN-Aggregate-Max-Bit rate-UL: 75000000    -   [O] Activation-Time    -   [O] Deactivation-Time

Example (1)

The AVPs in example (1) determine the default value for the APN-AMBR as75 Megabytes per second at Downlink traffic (DL) and 75 Megabytes persecond at Uplink traffic (UL). In addition, the AVPs of example 1determine an activation-time and deactivation-time for the PGW 107 forsetting a time for activation or deactivation of the APN-AMBR of the 75Megabytes per second.

In another implementation, the PCRF 103 may determine an activation-timeand a deactivation-time for the APN-AMBR of a customer device 111 a-111n based on a QoS class identifier (OCI). The QCI can define a prioritylevel for the customer device 111 a-111 n with respect to other customerdevices 111 a-111 n. Using the priority level, the PGW 107 can providedata to the customer device with higher priority before providing datato the customer device with lower priority level.

The QCI can be an integer from 1 to 9, indicating 9 different QoSperformance characteristics of each network data packet. QCI values arestandardized to reference specific QoS characteristics, and each QCIcontains standardized performance characteristics (values), such asresource type (Guaranteed Bit rate GBR or non-GBR), priority (1 to 9),Packet Delay Budget (allowed packet delay shown in values ranging from50 milliseconds to 300 milliseconds), Packet Error Loss Rate (allowedpacket loss shown in values from 10⁻² to 10⁻⁶.

Example (2) illustrates a sample of new optional functions added intothe Gx interface 115 standard for determining the activation-time andthe deactivation-time by the PCRF 103 based on the priority level. Theseexample AVPs provide information on when the QoS, QCI parameters andapplication and retention priorities (ARP) would be activated ordeactivated. The PGW 107 can use ARP values to manage the allocation andretention of resources for data services provided.

[V] Default-EPS-Bearer-QoS:

[V] [M] QoS-Class-Identifier: QCI_9 (9)

[V] Allocation-Retention-Priority:

[V] Priority-Level: 10

[V] Pre-emption-Capability: PRE-EMPTION_CAPABILITY_DISABLED (1)

[V] Pre-emption-Vulnerability: PRE-EMPTION_VULNERABILITY_DISABLED (1)

[O] Activation-Time

[O] Deactivation-Time

Example (2)

The aggregate maximum bit rate (AMBR) defines the maximum allowedthroughput for a customer device 111 a-111 n based on the sum of alltotal bit rates that all non-GBR data services associated with an accesspoint name (APN) are allowed to use. Thus, the AMBR limits the totalnon-GBR traffic for an APN. In example (2), the QCI parameter value 9and priority level 10 is assigned to the customer device 111 a-111 n.The pre-emption-capability and the pre-emption-vulnerability aredisabled in this example. The pre-emption can be enabled for the PGW 107to evaluate the priority level, pre-emption-vulnerability, andpreemption-capability flags to determine whether a data service is acandidate for deletion.

The pre-emption-capability AVP defines whether a service data flow canget resources that were already assigned to another service data flowwith a lower priority level. The pre-emption-capability can have a value(0) or “enabled” or a value (1) or disabled. The enabled value (0)indicates that the service data flow is allowed to get resources thatwere already assigned to another service data flow with a lower prioritylevel. The disabled values (1) indicates that the service data flow isnot allowed to get resources that were already assigned to anotherservice data flow with a lower priority level.

The pre-emption-vulnerability AVP defines whether a service data flowcan lose the resources assigned to it in order to admit a service dataflow with higher priority level. The pre-emption-vulnerability can havea value (0) or “enabled” or a value (1) or disabled. The enabled value(0) indicates that the resources assigned to the service data flow canbe pre-empted and allocated to a service data flow with a higherpriority level. The disabled values (1) indicates that the resourcesassigned to the service data flow shall not be pre-empted and allocatedto a service data flow with a higher priority level.

The AVPs of example 2 can be defined for each customer device 111 a-111n such that the PGW 107 can determine which customer device to providedata service to, based on a comparison between the QCI value andpriority level for various customer devices requesting data service.

In another implementation, the PCRF 103 may determine an activation-timeand a deactivation-time for the APN-AMBR of a customer device 111 a-111n based on a conditional APN-AMBR value for the customer device 111a-111 n. For example, a condition may be defined by policy makers or bythe service provider to update the APN-AMBR for one or more customerdevices 111 a-111 n based on that condition. The conditional APN-AMBRmay be applied to radio access technology (RAT-Type) AVPs or enumerated,connectivity access network (IPCAN-Type) AVPs. The condition may includea time of the day, a day of the month, a specific date, a location ofthe customer device, a data plan of the customer device, etc. Using thecondition, the PGW 107 can provide data to the customer device based onwhether the condition holds or do not hold.

Example (3) illustrates a sample of new optional functions added intothe Gx interface 115 standard for determining the activation-time andthe deactivation-time by the PCRF 103 based on a conditional APN-AMBR.These example AVPs provide information on when the QoS, QCI parametersand application and retention priorities (ARP) would be activated ordeactivated. The PGW 107 can use ARP values to manage the allocation andretention of resources for data services provided.

-   -   Conditional-APN-Aggregate-Max-Bit rate:    -   APN-Aggregate-Max-Bit rate-DL: 75000000    -   APN-Aggregate-Max-Bit rate-UL: 75000000    -   RAT-Type: EUTRAN    -   [O] Activation-Time    -   [O] Deactivation-Time

Example (3)

The Example (3) indicates that, if RAT-Type is Evolved UniversalTerrestrial Radio Access Network (EUTRAN), the PGW 107 should enforce anAPN-AMBR of 75000000.

The structure, programming and operations of the various types of mobiledevices are well known. However, for completeness, it may be useful toconsider the functional elements/aspects of two exemplary customerdevices 111 a-111 n, at a high-level.

For purposes of such a discussion, FIG. 5 is a high-level functionalblock diagram of an exemplary non-touch type mobile device (e.g.,customer device 111 a-111 n) that may utilize the enforced quality ofservice parameters through a network/system like that shown in FIG. 1.Although the customer device 111 a-111 n may be a smart-phone or may beincorporated into another device, such as a personal digital assistant(PDA) or the like, for discussion purposes, the illustration shows thecustomer device 111 a-111 n is in the form of a handset. The handsetimplementation of the customer device 111 a-111 n functions as a normaldigital wireless telephone station. For that function, the station 111a-111 n includes a microphone 102 for audio signal input and a speaker104 for audio signal output. The microphone 102 and speaker 104 connectto voice coding and decoding circuitry (vocoder) 106. For a voicetelephone call, for example, the vocoder 106 provides two-way conversionbetween analog audio signals representing speech or other audio anddigital samples at a compressed bit rate compatible with the digitalprotocol of wireless telephone network communications or voice overpacket (Internet Protocol) communications.

For digital wireless communications, the handset 111 a-111 n alsoincludes at least one digital transceiver (XCVR) 108. Today, the handset111 a-111 n would be configured for digital wireless communicationsusing one or more of the common network technology types. The conceptsdiscussed here encompass implementations of the customer device 111a-111 n utilizing any digital transceivers that conform to current orfuture developed digital wireless communication standards. The customerdevice 111 a-111 n may also be capable of analog operation via a legacynetwork technology.

The transceiver 108 provides two-way wireless communication ofinformation, such as vocoded speech samples and/or digital information,in accordance with the technology of the network 109. The transceiver108 also sends and receives a variety of signaling messages in supportof the various voice and data services provided via the customer device111 a-111 n and the communication network. Each transceiver 108 connectsthrough RF send and receive amplifiers (not separately shown) to anantenna 110. The transceiver may also support various types of mobilemessaging services, such as short message service (SMS), enhancedmessaging service (EMS) and/or multimedia messaging service (MMS).

The customer device 111 a-111 n includes a display 118 for displayingmessages, menus or the like; call related information dialed by theuser, calling party numbers, etc. A keypad 120 enables dialing digitsfor voice and/or data calls as well as generating selection inputs, forexample, as may be keyed-in by the user based on a displayed menu or asa cursor control and selection of a highlighted item on a displayedscreen. The display 118 and keypad 120 are the physical elementsproviding a textual or graphical user interface. Various combinations ofthe keypad 120, display 118, microphone 102 and speaker 104 may be usedas the physical input output elements of the graphical user interface(GUI), for multimedia (e.g., audio and/or video) communications. Ofcourse, other user interface elements may be used, such as a trackball,as in some types of PDAs or smart phones.

In addition to normal telephone and data communication relatedinput/output (including message input and message display functions),the user interface elements also may be used for display of menus andother information to the user and user input of selections, includingany needed during the process for enforcing quality of serviceparameters.

A microprocessor 112 serves as a programmable controller for thecustomer device 111 a-111 n, in that it controls all operations of thecustomer device 111 a-111 n in accord with programming that it executes,for all normal operations, and for operations involved in the enforcedquality of service parameters under consideration here. In the example,the customer device 111 a-111 n includes flash type program memory 114,for storage of various “software” or “firmware” program routines andmobile configuration settings, such as mobile directory number (MDN)and/or mobile identification number (MIN), etc. The customer device 111a-111 n may also include a non-volatile random access memory (RAM) 116for a working data processing memory. Of course, other storage devicesor configurations may be added to or substituted for those in theexample. In a present implementation, the flash type program memory 114stores firmware such as a boot routine, device driver software, anoperating system, call processing software and vocoder control software,and any of a wide variety of other applications, such as client browsersoftware and short message service software. The memories 114, 116 alsostore various data, such as telephone numbers and server addresses,downloaded data such as multimedia content, and various data input bythe user. Programming stored in the flash type program memory 114,sometimes referred to as “firmware,” is loaded into and executed by themicroprocessor 112.

For purposes of such a discussion, FIG. 6 is a high-level functionalblock diagram of an exemplary touch screen type mobile device (e.g.,customer device 111 a-111 n) that may utilize the enforced quality ofservice parameters through a network/system like that shown in FIG. 1.Although possible configured somewhat differently, at least logically, anumber of the elements of the exemplary touch screen type customerdevices 111 a-111 n are similar to the elements of customer device 111a-111 n, and are identified by like reference numbers in FIG. 6. Forexample, the touch screen type customer devices 111 a-111 n includes amicrophone 102, speaker 104 and vocoder 106, for audio input and outputfunctions, much like in the earlier example. The customer devices 111a-111 n also includes at least one digital transceiver (XCVR) 108, fordigital wireless communications, although the handset 111 a-111 n mayinclude an additional digital or analog transceiver. The conceptsdiscussed here encompass implementations of the customer devices 111a-111 n utilizing any digital transceivers that conform to current orfuture developed digital wireless communication standards. As in thestation 111 a-111 n, the transceiver 108 provides two-way wirelesscommunication of information, such as vocoded speech samples and/ordigital information, in accordance with the technology of the network109. The transceiver 108 also sends and receives a variety of signalingmessages in support of the various voice and data services provided viathe customer devices 111 a-111 n and the communication network. Eachtransceiver 108 connects through RF send and receive amplifiers (notseparately shown) to an antenna 110. The transceiver may also supportvarious types of mobile messaging services, such as short messageservice (SMS), enhanced messaging service (EMS) and/or multimediamessaging service (MMS).

As in the example of station 111 a-111 n, a microprocessor 112 serves asa programmable controller for the customer devices 111 a-111 n, in thatit controls all operations of the customer devices 111 a-111 n in accordwith programming that it executes, for all normal operations, and foroperations involved in the procedure for enforcing quality of serviceparameters under consideration here. In the example, the customerdevices 111 a-111 n includes flash type program memory 114, for storageof various program routines and mobile configuration settings. Thecustomer devices 111 a-111 n may also include a non-volatile randomaccess memory (RAM) 116 for a working data processing memory. Of course,other storage devices or configurations may be added to or substitutedfor those in the example. Hence, outlined above, the customer devices111 a-111 n includes a processor, and programming stored in the flashmemory 114 configures the processor so that the mobile device is capableof utilizing enforced quality of service parameters.

In the example of FIG. 6, the user interface elements included a displayand a keypad. The customer devices 111 a-111 n may have a limited numberof key 130, but the user interface functions of the display and keypadare replaced by a touch screen display arrangement. At a high level, atouch screen display is a device that displays information to a user andcan detect occurrence and location of a touch on the area of thedisplay. The touch may be an actual touch of the display device with afinger, stylus or other object, although at least some touch screens canalso sense when the object is in close proximity to the screen. Use of atouch screen display as part of the user interface allows a user tointeract directly with the information presented on the display.

Hence, the exemplary customer devices 111 a-111 n includes a display122, which the microprocessor 112 controls via a display driver 124, topresent visible outputs to the device user. The customer devices 111a-111 n also includes a touch/position sensor 126. The sensor 126 isrelatively transparent, so that the user may view the informationpresented on the display 122. A sense circuit 128 sensing signals fromelements of the touch/position sensor 126 and detects occurrence andposition of each touch of the screen formed by the display 122 andsensor 126. The sense circuit 128 provides touch position information tothe microprocessor 112, which can correlate that information to theinformation currently displayed via the display 122, to determine thenature of user input via the screen.

The display 122 and touch sensor 126 (and possibly one or more keys 130,if included) are the physical elements providing the textual andgraphical user interface for the customer devices 111 a-111 n. Themicrophone 102 and speaker 104 may be used as additional user interfaceelements, for audio input and output, including with respect to somefunctions related to the enforcement of quality of service parameters.

The structure and operation of the customer devices 111 a-111 n, asoutlined above, were described by way of example, only. As shown by theabove discussion, functions relating to the enforced quality of serviceparameters, via a graphical user interface of a mobile device may beimplemented on computers connected for data communication via thecomponents of a packet data network, operating as shown in FIG. 1.Although special purpose devices may be used, such devices also may beimplemented using one or more hardware platforms intended to represent ageneral class of data processing device commonly used to run “server”programming so as to implement the enforced quality of serviceparameters functions discussed above, albeit with an appropriate networkconnection for data communication.

As known in the data processing and communications arts, ageneral-purpose computer typically comprises a central processor orother processing device, an internal communication bus, various types ofmemory or storage media (RAM, ROM, EEPROM, cache memory, disk drivesetc.) for code and data storage, and one or more network interface cardsor ports for communication purposes. The software functionalitiesinvolve programming, including executable code as well as associatedstored data, e.g. files used for enforcing quality of serviceparameters. The software code is executable by the general-purposecomputer that functions as the gateway for enforcing quality of serviceparameters and/or that functions as a user terminal device. Inoperation, the code is stored within the general-purpose computerplatform. At other times, however, the software may be stored at otherlocations and/or transported for loading into the appropriategeneral-purpose computer system. Execution of such code by a processorof the computer platform enables the platform to implement themethodology for enforcing quality of service parameters, in essentiallythe manner performed in the implementations discussed and illustratedherein.

FIGS. 7 and 8 provide functional block diagram illustrations of generalpurpose computer hardware platforms. FIG. 7 illustrates a network orhost computer platform, as may typically be used to implement a server.FIG. 8 depicts a computer with user interface elements, as may be usedto implement a personal computer or other type of work station orterminal device, although the computer of FIG. 8 may also act as aserver if appropriately programmed. The structure, programming andgeneral operation of such computer equipment are well known and as aresult the drawings should be self-explanatory.

A server, for example, includes a data communication interface forpacket data communication. The server also includes a central processingunit (CPU), in the form of one or more processors, for executing programinstructions. The server platform typically includes an internalcommunication bus, program storage and data storage for various datafiles to be processed and/or communicated by the server, although theserver often receives programming and data via network communications.The hardware elements, operating systems and programming languages ofsuch servers are conventional in nature. Of course, the server functionsmay be implemented in a distributed fashion on a number of similarplatforms, to distribute the processing load.

A computer type user terminal device, such as a PC or tablet computer,similarly includes a data communication interface CPU, main memory andone or more mass storage devices for storing user data and the variousexecutable programs (see FIG. 8). A mobile device type user terminal mayinclude similar elements, but will typically use smaller components thatalso require less power, to facilitate implementation in a portable formfactor. The various types of user terminal devices will also includevarious user input and output elements. A computer, for example, mayinclude a keyboard and a cursor control/selection device such as amouse, trackball, joystick or touchpad; and a display for visualoutputs. A microphone and speaker enable audio input and output. Somesmartphones include similar but smaller input and output elements.Tablets and other types of smartphones utilize touch sensitive displayscreens, instead of separate keyboard and cursor control elements. Thehardware elements, operating systems and programming languages of suchuser terminal devices also are conventional in nature.

Hence, aspects of the methods of providing enforced quality of serviceparameters outlined above may be embodied in programming. Programaspects of the technology may be thought of as “products” or “articlesof manufacture” typically in the form of executable code and/orassociated data that is carried on or embodied in a type of machinereadable medium. “Storage” type media include any or all of the tangiblememory of the computers, processors or the like, or associated modulesthereof, such as various semiconductor memories, tape drives, diskdrives and the like, which may provide non-transitory storage at anytime for the software programming. All or portions of the software mayat times be communicated through the Internet or various othertelecommunication networks. Such communications, for example, may enableloading of the software from one computer or processor into another.Thus, another type of media that may bear the software elements includesoptical, electrical and electromagnetic waves, such as used acrossphysical interfaces between local devices, through wired and opticallandline networks and over various air-links. The physical elements thatcarry such waves, such as wired or wireless links, optical links or thelike, also may be considered as media bearing the software. As usedherein, unless restricted to non-transitory, tangible “storage” media,terms such as computer or machine “readable medium” refer to any mediumthat participates in providing instructions to a processor forexecution.

Hence, a machine readable medium may take many forms, including but notlimited to, a tangible storage medium, a carrier wave medium or physicaltransmission medium. Non-volatile storage media include, for example,optical or magnetic disks, such as any of the storage devices in anycomputer(s) or the like, such as may be used to implement enforcing ofquality of service parameters, etc. shown in the drawings. Volatilestorage media include dynamic memory, such as main memory of such acomputer platform. Tangible transmission media include coaxial cables;copper wire and fiber optics, including the wires that comprise a buswithin a computer system. Carrier-wave transmission media can take theform of electric or electromagnetic signals, or acoustic or light wavessuch as those generated during radio frequency (RF) and infrared (IR)data communications. Common forms of computer-readable media thereforeinclude for example: a floppy disk, a flexible disk, hard disk, magnetictape, any other magnetic medium, a CD-ROM, DVD or DVD-ROM, any otheroptical medium, punch cards paper tape, any other physical storagemedium with patterns of holes, a RAM, a PROM and EPROM, a FLASH-EPROM,any other memory chip or cartridge, a carrier wave transporting data orinstructions, cables or links transporting such a carrier wave, or anyother medium from which a computer can read programming code and/ordata. Many of these forms of computer readable media may be involved incarrying one or more sequences of one or more instructions to aprocessor for execution.

While the foregoing has described what are considered to be the bestmode and/or other examples, it is understood that various modificationsmay be made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that the teachings may beapplied in numerous applications, only some of which have been describedherein. It is intended by the following claims to claim any and allapplications, modifications and variations that fall within the truescope of the present teachings.

Unless otherwise stated, all measurements, values, ratings, positions,magnitudes, sizes, and other specifications that are set forth in thisspecification, including in the claims that follow, are approximate, notexact. They are intended to have a reasonable range that is consistentwith the functions to which they relate and with what is customary inthe art to which they pertain.

The scope of protection is limited solely by the claims that now follow.That scope is intended and should be interpreted to be as broad as isconsistent with the ordinary meaning of the language that is used in theclaims when interpreted in light of this specification and theprosecution history that follows and to encompass all structural andfunctional equivalents. Notwithstanding, none of the claims are intendedto embrace subject matter that fails to satisfy the requirement ofSections 101, 102, or 103 of the Patent Act, nor should they beinterpreted in such a way. Any unintended embracement of such subjectmatter is hereby disclaimed.

Except as stated immediately above, nothing that has been stated orillustrated is intended or should be interpreted to cause a dedicationof any component, step, feature, object, benefit, advantage, orequivalent to the public, regardless of whether it is or is not recitedin the claims.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”or any other variation thereof, are intended to cover a non-exclusiveinclusion, such that a process, method, article, or apparatus thatcomprises a list of elements does not include only those elements butmay include other elements not expressly listed or inherent to suchprocess, method, article, or apparatus. An element proceeded by “a” or“an” does not, without further constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises the element.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage, and use of such information may be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various examples for the purpose of streamlining thedisclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claims require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed example. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separately claimed subject matter.

What is claimed is:
 1. A method comprising: receiving, at a gateway andfrom a mobile device, a request for data usage, wherein the request isreceived at the gateway over a communication network; in response toreceiving the request for data usage, sending from the gateway to acontroller an inquiry for an allowed bit rate associated with the mobiledevice; in response to sending the inquiry for the allowed bit rate,receiving at the gateway, a first bit rate value as the allowed bit rateassociated with the mobile device; upon receiving the first bit ratevalue, sending from the gateway to a charging system a request for aquota associated with the mobile device, wherein the quota indicates anamount of data the mobile device is allowed to use; in response to therequest for the quota associated with the mobile device, receiving atthe gateway the quota from the charging system; in response to receivingthe quota from the charging system, enabling the mobile device to accessdata on the communication network based on the first bit rate valueuntil the quota is reached; subsequent to the quota being reached,identifying that a data usage threshold is reached; subsequent toidentifying that a data usage threshold is reached, receiving, at thegateway and from the controller, a second bit rate value as the allowedbit rate associated with the mobile device; in response to receiving thesecond bit rate value, enabling the mobile device to access data on thecommunication network based on the second bit rate value until apredefined activation time is reached; and resetting the second bit ratevalue for the mobile device to the first bit rate value when thepredefined activation time is reached, wherein identifying that a datausage threshold is reached comprises receiving, at the gateway and fromthe controller, a first notification indicating that the data usagethreshold is reached, the first notification being responsive to asecond notification received at the controller from the charging systemindicating that the data usage threshold is reached.
 2. The method ofclaim 1, wherein: receiving the quota from the charging system includes,receiving at the gateway, quota and a validity time for usage of thequota by the mobile device from the charging system, the quota includinga slice of a remaining available quota associated with the mobile deviceuntil the data usage threshold is reached, the method furthercomprising: sending from the gateway to the charging system a requestfor an updated quota once the quota is reached; in response to therequest for the updated quota, receiving at the gateway and from thecharging system, the updated quota, the updated quota corresponding tothe remaining available quota associated with the mobile device untilthe data usage threshold is reached; and in response to receiving theupdated quota from the charging system, enabling the mobile device toaccess data on the communication network based on the first bit ratevalue until the data usage threshold is reached.
 3. The method of claim1, wherein identifying that the data usage threshold is reachedincludes: repeatedly sending the request for the quota to the chargingsystem, receiving the quota from the charging system, and providing datato the mobile device based on the first bit rate, until the chargingsystem indicates that the data usage threshold is reached.
 4. The methodof claim 1, wherein the gateway is a Packet Data Network Gateway (PGW),the controller is a Policy Control and Charging Rules Function (PCRF),and the charging system is an Online Charging System (OCS).
 5. Themethod of claim 4, wherein sending the inquiry from the PGW to the PCRFincludes sending the inquiry via a Gx interface, sending the requestfrom the PGW to the OCS includes sending the request via a Gy interface,and the second notification is received at the PCRF from the OCS via aSy interface.
 6. The method of claim 1, wherein sending the inquiry forthe allowed bit rate includes sending the inquiry for an allowed maximumbit rate associated with the mobile device.
 7. The method of claim 6,wherein the allowed maximum bit rate includes Access Point NameAggregate maximum Bit Rate (APN-AMBR).
 8. The method of claim 1, whereinthe predefined activation time includes start of a new billing cycle. 9.The method of claim 1, further comprising: determining that a predefineddeactivation time is reached; and upon determining that the predefinedeactivation time is reached, resetting the allowed bit rate to thesecond bit rate value.
 10. The method of claim 1, wherein resetting thesecond bit rate value to the first bit rate value comprises: receiving arevalidation notification for the mobile device, at the gateway, therevalidation notification including a request to revalidate the allowedbit rate associated with the mobile device at a time indicated in thenotification; and providing data to the mobile device based on therevalidated allowed bit rate.
 11. A method comprising: receiving, at agateway and from a mobile device, a request for data usage, wherein therequest is received at the gateway over a communication network; inresponse to receiving the request for data usage, sending from thegateway to a controller, an inquiry for an allowed bit rate and adefault priority level associated with the mobile device; in response tosending the inquiry for the allowed bit rate and the default prioritylevel, receiving, at the gateway, a first bit rate value as the allowedbit rate and the default priority level associated with the mobiledevice; upon receiving the first bit rate value as the allowed bit rateand the default priority level, sending from the gateway to a chargingsystem, a request for a quota associated with the mobile device, whereinthe quota indicates an amount of data the mobile device is allowed touse; in response to the request for the quota associated with the mobiledevice, receiving, at the gateway, the quota and a validity time fromthe charging system, the quota received from the charging systemincluding a slice of a remaining available quota associated with themobile device prior to a data usage threshold for the mobile devicebeing reached; in response to receiving the quota from the chargingsystem, enabling the mobile device to access data on the communicationnetwork based on the first bit rate value and the default priority leveluntil the quota is reached or the validity time is expired; subsequentto the quota being reached or the validity time being expired,determining that the data usage threshold for the mobile device isreached; upon determining the data usage threshold for the mobile deviceis reached, receiving, at the gateway and from the controller, a secondbit rate value as the allowed bit rate and a second priority levelassociated with the mobile device; enabling the mobile device to accessdata on the communication network based on the second bit rate valueover one or more mobile devices having a lower priority level than thesecond priority level until a predefined activation time is reached; andwhen the predefined activation time is reached, resetting the secondallowed bit rate value for the mobile device to the first bit rate valueand resetting the second priority level to the default priority level.12. The method of claim 11, wherein determining that the data usagethreshold is reached includes: repeatedly sending the request for thequota to the charging system, receiving the quota from the chargingsystem, and providing data to the mobile device, until the chargingsystem indicates that the data usage threshold is reached.
 13. Themethod of claim 11, wherein sending the inquiry for the allowed bit rateincludes sending the inquiry for an allowed maximum bit rate associatedwith the mobile device.
 14. The method of claim 11, wherein thepredefined activation time includes start of a new billing cycle. 15.The method of claim 11, further comprising receiving, at the gateway andfrom the controller, a plurality of quality of service (QoS) parametersfor the mobile device, the plurality of QoS parameters including one ormore conditions.
 16. The method of claim 11, wherein resetting thesecond bit rate value to the first bit rate value comprises: receiving arevalidation notification for the mobile device, at the gateway, therevalidation notification including a request to revalidate the allowedbit rate associated with the mobile device at a time indicated in thenotification; and providing data to the mobile device based on therevalidated allowed bit rate.
 17. A system comprising: a processingdevice; and a memory storing executable instructions that, when executedby the processing device, cause the processing device to: receive from amobile device, a request for data usage, wherein the request is receivedover a communication network; in response to receiving the request fordata usage, send to a controller, an inquiry for an allowed bit rate anda default priority level associated with the mobile device; in responseto sending the inquiry for the allowed bit rate and the default prioritylevel, receive a first bit rate value as the allowed bit rate and thedefault priority level associated with the mobile device; upon receivingthe first bit rate value as the allowed bit rate and the defaultpriority level, send to a charging system, a request for a quotaassociated with the mobile device, wherein the quota indicates an amountof data the mobile device is allowed to use; in response to the requestfor the quota associated with the mobile device, receive the quota fromthe charging system, the quota received from charging system including aslice of a remaining available quota associated with the mobile deviceprior to a data usage threshold being reached; in response to receivingthe quota from the charging system, enable the mobile device to accessdata on the communication network based on the first bit rate value andthe default priority level until the quota is reached; receive from thecontroller, a conditional parameter and a second bit rate value as theallowed bit rate associated with the mobile device, once the data usagethreshold for the mobile device is reached subsequent to the quota beingreached; when the conditional parameter indicates that the mobile deviceis to receive the data, enable the mobile device to access data on thecommunication network based on the second bit rate value until apredefined activation time is reached; and when the predefinedactivation time is reached, reset the second bit rate value for themobile device to the first bit rate value.
 18. The method of claim 17,wherein to identify that the data usage threshold is reached the memoryfurther includes instructions that, when executed by the processingdevice, cause the processing device to: repeatedly send the request forthe quota to the charging system, receive the quota from the chargingsystem, and provide data to the mobile device, until the charging systemindicates that the data usage threshold is reached.
 19. The system ofclaim 17, wherein the predefined activation time includes start of a newbilling cycle.
 20. The system of claim 17, wherein the memory furtherincludes instructions that, when executed by the processing device,cause the processing device to receive a validity time from the chargingsystem along with the first bit rate value, wherein to enable the mobiledevice to access data on the communication network based on the firstbit rate value, the memory further includes instructions that, whenexecuted by the processing device, cause the processing device to enablethe mobile device access to data until the validity time is expired.